Method to determine the jurisdiction of cmrs traffic via cell site location and rate center

ABSTRACT

A method includes receiving, at a processor, Call Detail Records (CDRs) from a Data Mediation System, in which each CDR includes a called party number (CdPN) associated with a first device, and a Cell Site ID associated with a location of a cell carrying a communication from a second device. Also included are: obtaining, from a first digital table, a first Major Trading Area (MTA) associated with the CdPN; obtaining, from a second digital table, a second MTA associated with the Cell Site ID; and concluding that the first and second devices are communicating in Local Traffic, if the first MTA is the same as the second MTA. 
     The method may also conclude that the first and second devices are communicating in Long Distance Traffic, if the first MTA and second MTA are not the same.

BACKGROUND

Within the telecommunications industry, interconnection is the physicallinking of a carrier's network with equipment or facilities notbelonging to that network for the exchange of telecommunications trafficsuch as a voice call. The term may refer to a connection between acarrier's facilities and the equipment belonging to its customer, or toa connection between carriers. The interconnection between carriers alsoinvolves different rates, known as Minute-of-Usage (MOU) rates, whichare applied to the voice traffic exchanged. The MOU rates depend onidentifying the jurisdiction of the voice traffic exchanged. Thejurisdiction may be either Local (also referred to as non-Access) orLong Distance (also referred to as Access). The Federal CommunicationsCommission (FCC) has established MOU rates covering compensation betweencarriers or providers exchanging telecommunications traffic(compensation regarding the origination and termination of calls betweencarriers/providers).

Conventionally, MOU rates are applied to the voice traffic exchanged.The FCC, however, has established that Bill-and-Keep (B&K) applies toLocal Traffic, or non-Access Traffic exchanged between a CommercialMobile Radio Service (CMRS) Provider, such as Verizon Wireless®, and aRural Local Exchange Company (RLEC). B&K, or BAK, is a pricingarrangement for the interconnection of two telecommunications networksunder which the reciprocal call termination charge is zero. That is,each network agrees to terminate calls from the other network at nocharge or the equivalent rate of $0.00 per MOU. Positive MOU rates(greater than $0.0) remain applicable to the Long Distance Traffic, orAccess Traffic, exchanged between a CMRS Provider and an RLEC.

As a result, accurately determining the jurisdiction of a call exchangedbetween a CMRS Provider and a Local Exchange Carrier (LEC) as beingeither Local (non-Access) Traffic, or Long Distance (Access)is requiredto validate network compensation, or expenses. A need also exists toverify the network compensation and identify opportunities to control,or reduce network expenses.

As will be explained, an aspect of the traffic tracking system of thepresent application identifies the jurisdiction of voice trafficexchanged between a CMRS Provider, such as Verizon Wireless®, andanother local provider, such as a Rural Local Exchange Carrier (RLEC).Another aspect of the traffic tracking system of the present applicationvalidates the network expenses of the CMRS Provider and identifiesopportunities to control or reduce network expenses.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawing figures depict one or more implementations in accord withthe present teachings, by way of example only, not by way of limitation.In the figures, like reference numerals refer to the same or similarelements.

FIG. 1 is a block diagram showing high-level functional aspects of atraffic tracking system;

FIG. 2 provides a block diagram overview of a public switching telephonenetwork, illustrating a CMRS Provider's Switch connected to an RLEC EndOffice through an intermediary switch, such as BellSouth Tandem.

FIG. 3 illustrates an example of a Call Detail Record (CDR) includingadded enriched fields;

FIG. 4 provides a block diagram of a provider's Data Mediation Systemcollecting call records and enriching the call records with additionaldata, in accordance with an aspect of the present application;

FIG. 5 a illustrates an example of a cell site table identifyingcorresponding Major Trading Areas (MTAs) that may be stored in adatabase of a CMRS Provider, in accordance with an aspect of the presentapplication;

FIGS. 5 b and 5 c illustrate examples of a Combined Table used to reacha decision of whether a call is inter-MTA Traffic or intra-MTA Traffic;

FIG. 6 is a flow diagram showing a method of the present application foridentifying whether a voice exchange is Local Traffic (non-Access) orLong Distance Traffic (Access),

FIG. 7 illustrates a network or host computer platform, as may typicallybe used to implement a server; and

FIG. 8 depicts a computer with user interface elements, as may be usedto implement a personal computer, or another type of workstation, orterminal device.

DETAILED DESCRIPTION

In the following detailed description, specific details are set forth byway of examples in order to provide a thorough understanding of therelevant teachings. However, it should be apparent that the presentteachings may be practiced without such details. In other instances,well known methods, procedures, components, and/or circuitry have beendescribed at a relatively high level, without detail, in order to avoidunnecessarily obscuring aspects of the present teachings.

As will be explained, the traffic tracking system of the presentapplication may perform several types of enrichment on Call DetailRecords (CDRs). The relevant CDRs are generated by the CMRS Provider'stelecommunications switch, collected by the CMRS Provider's DataMediation System, and stored in the CMRS Provider's database.

FIG. 1 provides a high-level illustration of a traffic tracking system.Typically, customers using subscriber devices, such as mobile telephone2 b, make calls through the Public Switching Telephone Network (PSTN) 3.The Mobile Traffic Network 4 that originates the call uses certainmonitoring equipment to accumulate Call Detail Records (CDRs) 5. EachCDR includes a wide variety of information including the calling andcalled party numbers, the time of the call, the duration of the call ifcompleted, the type of release if terminated without completion,identification of office(s) serving the call, etc.

In the example shown in FIG. 1, Mobile Traffic Network 4 communicateswith PSTN 3. For the sake of simplicity, only two mobile stations (MSs)2 a and 2 b are shown communicating through Mobile Traffic Network 4, byway of two base stations (BSs) 6. Other Networks 8, using mobile station(MS) 2 c, are shown communicating with Mobile Traffic Network 4 and PSTN3. As an example, Mobile Traffic Network 4 may be a CMRS Provider (e.g.,Verizon Wireless®) and Other Networks 8 may be other additionalproviders. It will be understood that Mobile Traffic Network 4 and OtherNetworks 8 may accumulate Call Detail Records 5 without transmittingthrough PSTN 3.

The Mobile Traffic Network 4 allows users of mobile stations 2 a and 2 b(and other mobile stations not shown) to initiate and receive telephonecalls to each other, as well as through PSTN 3 when using telephonesconnected to the PSTN. The networks 4 and 8 typically also offer avariety of data services, via a global network (e.g., the Internet),such as downloads, web browsing, email, etc.

The networks 4 and 8 may be implemented by a number of interconnectednetworks. They may include Radio Access Networks (RANs), as well as aWide Area Network (WAN) interconnecting regional ground networks to corenetwork elements. A regional portion of network 4, such as that servingmobile stations 2 a and 2 b, may include one or more RANs and a regionalcircuit and/or packet switched network and associated signalingfacilities.

Physical elements of a RAN operated by one of the mobile serviceproviders or carriers include a number of base stations represented bybase stations (BSs) 6. Although not separately shown, base station 6 mayinclude a Base Transceiver System (BTS), which may communicate via anantennae system at the site of the base station and over an airlink withone or more mobile stations 2 a and 2 b. Each base station may include aBTS coupled to several antennae mounted on a radio tower within acoverage area, often referred to as a “cell.” The Other Networks 8 mayalso include a traffic network which carries communications between basestations and other elements. It will be understood that the variousnetwork elements may communicate with each other and other networks(e.g., PSTN 3 and the Internet) either directly, or indirectly.

Although not shown, a provider or carrier may also operate a number ofsystems that provide ancillary functions in support of the communicationservices provided through mobile data networks 4 and 8, and thoseelements may communicate with other nodes or elements in the system, viaone or more private packet data networks (sometimes referred to as anIntranet). Examples of such systems may include one or more applicationservers and related servers.

The Call Detail Records (CDRs) 5 supplied from Mobile Traffic Network 4(the CMRS Provider) may be sent to the CMRS Provider's Data MediationSystem 50. The Data Mediation System 50 may potentially collect CDRsfrom PSTN 3, or Other Networks 8. Networks, however, do not alwaysgenerate the same types of CDRs (or CDRs of the same format), andproviders are typically required to pay fees to obtain CDRs from anotherprovider's network. As a result, the carrier originating the traffic,i.e. the CMRS Provider, typically relies on the CDRs generated from itsown network (its own telecommunication equipment). Information containedin the CDRs may be loaded into appropriate tables in one or moredatabases. Further processing, however, may be needed to allow analysisand output of the results in desired aggregate forms. Thus, informationfrom Data Mediation System 50 may be prepared and uploaded through WAN37 (for example) for input to a Decision Support Database 70. This mayinclude modifying the call details by application of reference data. Thereference data may include Local Exchange & Routing Guide (LERG) datasuch as the Operating Carrier Number (OCN), local call jurisdictiondata, and/or other information used to enrich the overall CDR data. Itwill be appreciated that the Data Mediation System and the DecisionSupport Database may be located in one system or separate systems andmay be coupled directly, without a WAN as an interface in between. Theprepared call details may be compiled into data reports for output to auser's terminal 9 (for example). The Database 70 may capture and storehigh level summary data which may be displayed through user terminal 9in a variety of ways.

The traffic tracking system of the present application, thus, provideseffective collection and analysis of CDRs enriched with variousinformation. The CDRs required for analysis may be collected from asingle provider's network, without reliance on the use of CDRs fromanother provider's network. The enriched CDRs enable analysis of howtraffic is exchanged (directly or indirectly) between the CMRS Providerand another provider.

It may be helpful at this point to review the structure and operation ofa telephone network, at a relatively high level. Referring to FIG. 2,there is shown a block diagram of a switching telephone network. Ingeneral, the switched portion of the telephone network includes a seriesof telecommunication switches, which are conventionally referred to assignaling points (SPs). Certain of these SPs comprise End Offices (EOs),Mobile Switch Centers (MSCs), or Tandems. The telephone network mayinclude many segments operated by different carriers. For purposes ofthis discussion, FIG. 2 illustrates three such segments, orsub-networks. One sub-network is a CMRS Provider who controls MSC 20.The CMRS Provider may be Verizon Wireless®, for example. The secondsub-network is BellSouth, for example, who controls Tandem Switch 21.The third sub-network is represented by a Rural Local Exchange Company(RLEC) operating End Office Switch 22. Each sub-network may have its ownData Mediation System 50. The RLEC 22 may be another CMRS Provider andthe Tandem 21 may be an Intermediate Provider.

Still referring to FIG. 2, the CMRS Provider's MSC 20, BellSouth Tandem21 and RLEC End Office 22 are all located within the same Major TradingArea (MTA) 23. There are 51 MTAs located across the U.S. As shown, BaseStation 6 a and mobile phone 2 d are both located in MTA 23. The wiredtelephone 1 a is also located in MTA 23. Base Station 6 b and mobilephone 2 c, on the other hand, are both located in another MTA (notlabeled). According to FCC rules, voice traffic exchanged between mobilephone 2 d and wire-line phone 1 a is considered an intra-MTA call.Although the voice traffic exchanged is routed through CMRS Provider'sMSC 20, BellSouth Tandem 21 and RLEC End Office 22, the entire exchangeis considered an intra-MTA call. The voice traffic exchanged betweencell phone 2 d and cell phone 2 c, however, which is routed through theCMRS Provider's MSC 20 and Base Station 6 b, is considered an inter-MTAcall.

The FCC also established traffic rates. Traffic to or from a CMRSProvider that originates and terminates within the same MTA is subjectto Local (non-Access) rates. Traffic which originates from within oneMTA and terminates within a different MTA is subject to Long Distance(Access) rates. Furthermore, the FCC transitioned rates for non-Accesstraffic exchanged with CMRS Providers to B&K, or BAK, or the equivalentMOU rate of $0. As a result, accurately determining the jurisdiction(non-Access or Access) of CMRS Provider's traffic is required tovalidate network expenses and identify opportunities to control orreduce expenses. The FCC, however, has never adopted a method foraccurately measuring the amount of Intra-MTA and Inter-MTA trafficexchanged between a CMRS Provider and various LECs. As a result, CMRSProviders and LECs negotiate factors which are intended to roughlyrepresent the amount (percentage) of non-Access (Intra-MTA) Traffic orAccess (Inter-MTA) Traffic. An aspect of the application which providesan accurate method of determining the jurisdiction of traffic exchangedbetween a CMRS Provider and a LEC will now be described.

When wireline carriers (LECs) exchange traffic between their networks,the Calling Party Number (CPN) and Called Party Number (CdPN) may beused to determine geographically where the call originated and where thecall terminated. This is possible because wire-line numbers are fixed(not mobile). The first six digits of the “number” (NPA-NXXs) of theCPNs and CdPNs may be used to derive a geographic location for theorigination and termination points of the call. The LECs may also useparameters, such as a Jurisdiction Information Parameter (JIP), which isan NPA-NXX assigned to a telecommunications switch to determine theorigination and termination points of a call. Therefore, the originationand termination points of LEC to LEC calls may be comparedgeographically to determine if a call is Local (non-Access) or LongDistance (Access). Since CMRS Providers' phones are mobile, the CPN(mobile subscriber's number) has no relationship to where a call mayoriginate. The use of a JIP to determine the jurisdiction of traffic maycreate inaccurate results, since a CMRS Provider's MSC may be located inone MTA and the CMRS Provider's mobile phones may be located in multipleMTAs.

An aspect of the method for determining accurate jurisdiction of trafficbetween a CMRS Provider and another provider, such as a LEC, uses datafields commonly found in a CDR and other data fields which may be usedto enrich the CDR. Turning first to the CDR, FIG. 3 shows an example ofa CDR collected by a CMRS Provider from a Mobile Switching Center (MSC).Generally, CDRs are created at the end of a call. By way of simplisticexample, a CDR describing a particular phone call may include the phonenumbers of both the calling and receiving parties, the start time, andduration of the call. Once collected, the CDRs are checked (validation),reformatted (normalization) and consolidated for further processing. Thecombined process of collection, validation, normalization andconsolidation is also referred to as Data Mediation.

The format in which CDRs are provided varies and is often configurable.Traditionally, the generating and handling of CDRs is known as AutomaticMessage Accounting or AMA which came into existence back in the 1940s.Today, telecommunications switches in North America generate CDRs in theAMA format. The number (quantity) of data fields and informationcontained in the data fields of AMA formatted CDRs may vary based on thetype of call (Local, Long Distance, Operator Services, International,Emergency, etc.) processed by a telecommunication switch. CDRs generatedby telecommunication switches commonly include data fields containingthe following information:

-   -   a) a unique sequence number identifying the CDR (Sequence        Number),    -   b) the phone number of the subscriber originating the call        (Calling Party or CPN),    -   c) the phone number receiving the call (Called Party or CdPN),    -   d) the starting time of the call (date and time),    -   e) the call duration (start to end time of the call),    -   f) the billing phone number that is charged for the call        (Charging Number or CN),    -   g) the disposition or the results of the call, indicating, for        example, whether or not the call was connected (Disposition),    -   h) the route by which the call left the telecommunication switch        (Trunk Group Number), and    -   i) any fault condition encountered (Fault Code or Cause Code).

In FIG. 3, three common data fields in the CDR are of interest to anaspect of the present method, namely, the CdPN, the Cell Site ID, andthe Call Minutes of Usage (MOU).

Other data fields containing more relevant information may be added to aCDR, thereby growing the number of data fields associated with the CDRand, thus, enriching the information contained in the CDR. FIG. 3 showseach CDR identified by a unique sequence number, including a CdPN MTA,which identifies the MTA associated with the CdPN. The CdPN MTA andother data fields may be appended to the common CDR data fields.

Referring next to FIG. 4, there is shown a system for enriching andanalyzing CDR data to determine the jurisdiction of CMRS traffic, wherethe CMRS Provider may be Verizon Wireless® (for example). A MobileSwitching Center (MSC) of a CMRS Provider, such as MSC 20 (also shown inFIG. 2) is shown communicating with Data Mediation System 50, the latterprocessing call details 5 (FIG. 1) and generating a CDR for each calltransacted by MSC 20. The CDR includes the Called party Number (CdPN).The CdPN may be, for example, a 10 digit telephone number conventionallyused in the U.S. (770-203-XXXX). The CDR also includes the Cell Site IDwhich generated the call through the CMRS Provider's MSC 20. The CDRalso includes the call MOU which identifies the minutes used in thecommunication exchange between the CMRS Provider's MSC and anotherprovider's Switch (for example, RLEC End Office 22 (FIG. 2)).

The Telcordia Local Exchange Routing Guide (LERG) 54 includes MTA dataof the CdPN. This data may be added as enriched data to the common CDRdata, as shown in FIG. 3. The data identifies the MTA in which the CdPNis located and, as explained below, may be used by Database (forexample, the Verizon Wireless® MARS Database) 70 to determine thejurisdiction of the communication exchange. An example of the data fieldindicating the MTA of the CdPN is shown in column F of the CombinedTable depicted in FIG. 5 b. It will be appreciated that columns C, D andE of the Combined Table show the aforementioned common CDR data fields,namely, Cell Site ID (column C), call MOU (column D) and CdPN (columnF), respectively.

Another table, referred to herein as the Cell Site Table, is shown inFIG. 5 b which may be tabulated by a CMRS Provider, such as VerizonWireless®. As shown, Table 52 may be compiled to list the Cell SiteIdentifications (IDs) and the MTA associated with each Cell Site ID.These data fields are shown in Columns A and B of FIG. 5 a.

Having described the data fields in the Combined Table of FIG. 5 a, amethod of determining jurisdiction of CMRS Traffic is now described. Themethod combines specific information regarding the location of a CellSite (the MTA in which the CMRS Provider's Cell Site is located withdata from CDRs collected by the CMRS Provider's MSC to determine the MTAof the Cell Site and the MTA of the LEC CdPN. The combined data may beanalyzed (sorted) to accurately identify (measure) the Intra-MTA(non-Access) Traffic and Inter-MTA (Access) Traffic exchanged betweenthe CMRS Provider and a LEC. As shown in FIG. 6, various steps may beused to measure the amount of Intra-MTA Traffic and Inter-MTA Traffic.

Based on the location of Cell Sites and MTA boundaries, Step 1 (S1)determines the MTA in which each Cell Site is located. A table iscompiled which lists the Cell Site Identification (ID) and the MTAassociated with each Cell Site (MTA in which each Cell Site is located).FIG. 5 a provides an example of a table format.

From the CDRs generated by an MSC, Step 2 (S2) identifies the followingkey parameters contained in each CDR:

Called Party Number (CdPN),

Cell site ID (Cell ID), and

Call Minutes of Usage (MOUs).

The Telcordia Local Exchange Routing Guide (LERG) lists the MTA in whichtelephone numbers of U.S. Carriers (Providers) are located. Within theLERG, each block or range of telephone numbers is associated with a RateCenter (RC) at an NPA-NXX level, where NPA-NXX is the first six (6)digits of a ten (10) digit telephone number. Each NPA-NXX is associatedwith an RC and each RC is associated with a MTA. Therefore, the NPA-NXXof a LEC CdPN is used by Step 3 (S3) to identify the RC of the LEC CdPNand determine the MTA in which the LEC CdPN is located.

Thus, from the CDRs, the method identifies the NPA-NXX of the LEC CdPN.Referencing the LERG, the method identifies the RC associated with eachCdPN NPA-NXX. Using the RC identified, the method determines the MTAassociated with each LEC CdPN NPA-NXX identified in Step 3 (S3).

Next, Step 4 (S4) matches data (associates data) using the Cell Site ID(Cell ID) in the CDR with the Cell Site ID and associated Cell Site MTAin the Cell Site Table; and the MTA of the LEC CdPN is associated withthe NPA-NXXs.

Leveraging the associated data within the Combined Table of FIG. 5 b,the method compares column B (Cell Site MTA (Cell Site Table)) withcolumn F (CdPN MTA (LERG)). When column B matches column F, the callrepresents an Intra-MTA (non-Access) call, since the call originates andterminates within the same MTA. When column B does not match column F,the call represents an Inter-MTA (Access) call, since the calloriginates in one MTA and terminates in a different MTA.

Using the associated data within the Combined Table, the methodidentifies the calls which are Intra-MTA (step S5) and the calls whichare Inter-MTA (step S6). This represents the jurisdictionalization ofthe call (call traffic), in which the jurisdiction may be eitherIntra-MTA (non-Access) or Inter-MTA (Access).

As shown in FIG. 5 c, the call between Cell Site ID SC1234 and CdPN678-555-1234 is an Inter-MTA call, since the call originates in one MTAand terminates in a different MTA. The other calls, however, areIntra-MTA calls, since the calls originate and terminate within the sameMTA.

The Call MOUs obtained from the Combined Table may be used to calculatethe amount (volume) of Inter-MTA Traffic, Intra-MTA Traffic, or overalltraffic. For the Inter-MTA calls identified, the method in Step 7 (S7),totals (sums) the associated Call MOUs to obtain the amount (volume) ofInter-MTA Traffic exchanged. This result may arbitrarily be called X.For the Intra-MTA calls identified, the methods in Step 8 (S8) totals(sums) the associated Call MOUs to obtain the amount (volume) ofIntra-MTA Traffic exchanged. This result may arbitrarily be callled Y.

Results X and Y may be used to validate the billing or claims from LECsregarding the amount of Inter-MTA Traffic or Intra-MTA Trafficexchanged, respectively. By totaling the Call MOUs associated with thecall traffic, the method may calculate, for example, that 22 MOUs arejurisdictionalized as Intra-MTA (non-Access) calls (traffic) and 25 MOUsare juridictionalized as Inter-MTA (Access) calls (traffic).

It will be appreciated that a CMRS Provider may exchange traffic with atleast one thousand (1,000) LECs. If a typical factor representating theamount of Inter-MTA Traffic (traffic subject to Access rates) is near8%; and if a typical MOU Access (Inter-MTA) rate is near $0.03/MOU, thena 1% change (reduction) in the amount of Inter-MTA Traffic may generateannual expense savings exceeding $10,800,000.00.

Large national CMRS Providers may have relationships with more than3,000 LECs and may achieve annual expense savings exceeding tens ofmillions of dollars, if their negotiated factors are overstating theamount of Access (Inter-MTA) traffic. Applying this method to determinethe jurisdiction of CMRS traffic via Cell Site location and Rate Centerensures accurate measurement of traffic and enables negotiation of lower(more appropriate) traffic factors and/or identifies opportunity toaddress compensation liability associated with traffic factors currentlyunderstating the amount of Access (Inter-MTA) traffic.

These general and specific aspects may be implemented using a system, amethod, a computer program, a computer readable medium, or an apparatusor any combination of systems, methods, computer programs, computerreadable mediums, and/or apparatuses.

As shown by the above discussion, functions relating to enriching CDRwith external data and analyzing the data may be implemented oncomputers connected for data communication via the components of apacket data network, operating with data mediation system 50 anddatabase 70, as shown in FIG. 1. Although special purpose devices may beused, such devices also may be implemented using one or more hardwareplatforms intended to represent a general class of data processingdevice commonly used to run “server” programming so as to implement theenrichment and reporting functions discussed above, albeit with anappropriate network connection for data communication.

As known in the data processing and communications arts, ageneral-purpose computer typically comprises a central processor orother processing device, an internal communication bus, various types ofmemory or storage media (RAM, ROM, EEPROM, cache memory, disk drivesetc.) for code and data storage, and one or more network interface cardsor ports for communication purposes. The software functionalitiesinvolve programming, including executable code as well as associatedstored data, e.g. files used for enriching the call records. Thesoftware code is executable by the general-purpose computer thatfunctions as the data mediation system 50 on a server device. Inoperation, the code is stored within the general-purpose computerplatform. At other times, however, the software may be stored at otherlocations and/or transported for loading into the appropriategeneral-purpose computer system. Execution of such code by a processorof the computer platform enables the platform to implement themethodology for enriching the call records with external data, inessentially the manner performed in the implementations discussed andillustrated herein.

FIGS. 7 and 8 provide functional block diagram illustrations of generalpurpose computer hardware platforms. FIG. 7 illustrates a network orhost computer platform, as may typically be used to implement a server.FIG. 8 depicts a computer with user interface elements, as may be usedto implement a personal computer or other type of work station orterminal device, although the computer of FIG. 8 may also act as aserver if appropriately programmed. It is believed that those skilled inthe art are familiar with the structure, programming and generaloperation of such computer equipment and as a result the drawings shouldbe self-explanatory.

A server, for example, includes a data communication interface forpacket data communication. The server also includes a central processingunit (CPU), in the form of one or more processors, for executing programinstructions. The server platform typically includes an internalcommunication bus, program storage and data storage for various datafiles to be processed and/or communicated by the server, although theserver often receives programming and data via network communications.The hardware elements, operating systems and programming languages ofsuch servers are conventional in nature, and it is presumed that thoseskilled in the art are adequately familiar therewith. Of course, theserver functions may be implemented in a distributed fashion on a numberof similar platforms, to distribute the processing load.

A computer type user terminal device, such as a PC or tablet computer,similarly includes a data communication interface CPU, main memory andone or more mass storage devices for storing user data and the variousexecutable programs (see FIG. 8). A mobile device type user terminal mayinclude similar elements, but will typically use smaller components thatalso require less power, to facilitate implementation in a portable formfactor. The various types of user terminal devices will also includevarious user input and output elements. A computer, for example, mayinclude a keyboard and a cursor control/selection device such as amouse, trackball, joystick or touchpad; and a display for visualoutputs. A microphone and speaker enable audio input and output. Somesmartphones include similar but smaller input and output elements.Tablets and other types of smartphones utilize touch sensitive displayscreens, instead of separate keyboard and cursor control elements. Thehardware elements, operating systems and programming languages of suchuser terminal devices also are conventional in nature, and it ispresumed that those skilled in the art are adequately familiartherewith.

Hence, aspects of the methods of enriching call records with other dataoutlined above and analyzing the data may be embodied in programming.Program aspects of the technology may be thought of as “products” or“articles of manufacture” typically in the form of executable codeand/or associated data that is carried on or embodied in a type ofmachine readable medium. “Storage” type media include any or all of thetangible memory of the computers, processors or the like, or associatedmodules thereof, such as various semiconductor memories, tape drives,disk drives and the like, which may provide non-transitory storage atany time for the software programming. All or portions of the softwaremay at times be communicated through the Internet or various othertelecommunication networks. Such communications, for example, may enableloading of the software from one computer or processor into another, forexample, from a management server or host computer of the telephoneservice provider into the computer platform of running the datapreparation process. Thus, another type of media that may bear thesoftware elements includes optical, electrical and electromagneticwaves, such as used across physical interfaces between local devices,through wired and optical landline networks and over various air-links.The physical elements that carry such waves, such as wired or wirelesslinks, optical links or the like, also may be considered as mediabearing the software. As used herein, unless restricted tonon-transitory, tangible “storage” media, terms such as computer ormachine “readable medium” refer to any medium that participates inproviding instructions to a processor for execution.

Hence, a machine readable medium may take many forms, including but notlimited to, a tangible storage medium, a carrier wave medium or physicaltransmission medium. Non-volatile storage media include, for example,optical or magnetic disks, such as any of the storage devices in anycomputer(s) or the like, such as may be used to implement the database70 shown in the drawings. Volatile storage media include dynamic memory,such as main memory of such a computer platform. Tangible transmissionmedia include coaxial cables; copper wire and fiber optics, includingthe wires that comprise a bus within a computer system. Carrier-wavetransmission media can take the form of electric or electromagneticsignals, or acoustic or light waves such as those generated during radiofrequency (RF) and infrared (IR) data communications. Common forms ofcomputer-readable media therefore include for example: a floppy disk, aflexible disk, hard disk, magnetic tape, any other magnetic medium, aCD-ROM, DVD or DVD-ROM, any other optical medium, punch cards papertape, any other physical storage medium with patterns of holes, a RAM, aPROM and EPROM, a FLASH-EPROM, any other memory chip or cartridge, acarrier wave transporting data or instructions, cables or linkstransporting such a carrier wave, or any other medium from which acomputer can read programming code and/or data. Many of these forms ofcomputer readable media may be involved in carrying one or moresequences of one or more instructions to a processor for execution.

While the foregoing has described what are considered to be the bestmode and/or other examples, it is understood that various modificationsmay be made therein and that the subject matter disclosed herein may beimplemented in various forms and examples, and that the teachings may beapplied in numerous applications, only some of which have been describedherein. It is intended by the following claims to claim any and allapplications, modifications and variations that fall within the truescope of the present teachings.

Unless otherwise stated, all measurements, values, ratings, positions,magnitudes, sizes, and other specifications that are set forth in thisspecification, including in the claims that follow, are approximate, notexact. They are intended to have a reasonable range that is consistentwith the functions to which they relate and with what is customary inthe art to which they pertain.

Except as stated immediately above, nothing that has been stated orillustrated is intended or should be interpreted to cause a dedicationof any component, step, feature, object, benefit, advantage, orequivalent to the public, regardless of whether it is or is not recitedin the claims.

It will be understood that the terms and expressions used herein havethe ordinary meaning as is accorded to such terms and expressions withrespect to their corresponding respective areas of inquiry and studyexcept where specific meanings have otherwise been set forth herein.Relational terms such as first and second and the like may be usedsolely to distinguish one entity or action from another withoutnecessarily requiring or implying any actual such relationship or orderbetween such entities or actions. The terms “comprises,” “comprising,”or any other variation thereof, are intended to cover a non-exclusiveinclusion, such that a process, method, article, or apparatus thatcomprises a list of elements does not include only those elements butmay include other elements not expressly listed or inherent to suchprocess, method, article, or apparatus. An element proceeded by “a” or“an” does not, without further constraints, preclude the existence ofadditional identical elements in the process, method, article, orapparatus that comprises the element.

What is claimed is:
 1. A method comprising: receiving, at a processor,Call Detail Records (CDRs) from a Data Mediation System, in which eachCDR includes a called party number (CdPN) associated with a firstdevice, and a Cell Site ID associated with a location of a cell carryinga communication from a second device; obtaining, from a first digitaltable, a first Major Trading Area (MTA) associated with the CdPN;obtaining, from a second digital table, a second MTA associated with theCell Site ID; and concluding that the first and second devices arecommunicating in Local traffic, if the first MTA is the same as thesecond MTA.
 2. The method of claim 1 further comprising: concluding thatthe first and second devices are communicating in Long Distance traffic,if the first MTA and second MTA are not the same.
 3. The method of claim1 wherein the first digital table is provided by a Local ExchangeRouting Guide (LERG), and the second digital table is provided by aMobile Switching Center (MSC) of a CMRS Provider.
 4. The method of claim3 including a database for storing data from the first and seconddigital tables.
 5. The method of claim 3 wherein the first digital tablelists an MTA of each telephone number of a Provider, and the seconddigital table lists an MTA of each Cell Site ID associated with the CMRSProvider.
 6. The method of claim 3 including the steps of: associatingeach telephone number listed in the first digital table with a RateCenter (RC), and associating each RC with an MTA.
 7. The method of claim1 including the step of: after concluding that the first and seconddevices are communicating in Local traffic, which is defined asnon-Access, then associating a zero dollar value to a Providerterminating the communication from the first device.
 8. The method ofclaim 1 including the steps of: concluding that the first and seconddevices are communicating in Long Distance traffic, which is defined asAccess, if the first MTA and second MTA are not the same, andassociating a dollar value to a Provider terminating the communicationfrom the first device.
 9. The method of claim 8 including the steps of:obtaining Minutes of Usage (MOU) from the CDR that is associated withthe Provider terminating the communication from the first device, andsumming the MOUs from the CDR that is associated with the Provider. 10.The method of claim 8 wherein the Provider of the first device is aLocal Exchange Company (LEC), and the second device is communicatingthrough the cell belonging to a CMRS Provider.
 11. A method ofdetermining jurisdiction of CMRS traffic through a cell site location,the method comprising the steps of: tabulating data in a first table, bya CMRS Provider, on Cell Site IDs and corresponding Major Trading Areas(MTAs), respectively, associated with the Cell Site IDs; obtaining aCalled Party Number (CdPN) from a Call Detail Record (CDR) of acommunication exchange between a Mobile Switching Center (MSC) of theCMRS Provider and a Rural Provider; determining a Rate Center (RC)associated with the CdPN; identifying a first MTA associated with theRC; obtaining a Cell Site ID from the CDR of the communication exchange;determining a second MTA corresponding to the Cell Site ID obtained fromthe CDR; if the first MTA and the second MTA are the same, thenconcluding that the jurisdiction of the CMRS traffic is Local, ornon-Access.
 12. The method of claim 11 wherein identifying the first MTAassociated with the CdPN includes: obtaining data from a second table,tabulated by a Local Exchange Routing Guide (LERG), the data includingMTAs corresponding to CdPNs, respectively.
 13. The method of claim 11further comprising the steps of: if the first MTA and the second MTA arenot the same, then concluding that the jurisdiction of the CMRS trafficis Long Distance, or Access.
 14. The method of claim 13 including thesteps of: obtaining a Minutes of Usage (MOU) from the CDR of thecommunication exchange; assigning the MOU to the Rural Provider, if thefirst and second MTAs are not the same; and assigning the MOU to theCMRS Provider, if the first and second MTAs are the same.
 15. The methodof claim 14 including the steps of: assigning each MOU from multipleCDRs to one or more Rural Providers, if the first and second MTAs arenot the same in each of the respective CDRs; and assigning each MOU fromthe multiple CDRs to the CMRS Provider, if the first and second MTAs arethe same in each of the respective CDRs.
 16. A server comprising: aprocessor, and a memory storing executable instructions for causing theprocessor to: receive Call Detail Records (CDRs) from a Data MediationSystem, in which each CDR includes a called party number (CdPN)associated with a first device, and a Cell Site ID associated with alocation of a cell carrying a communication from a second device;obtain, from a first table, a first Major Trading Area (MTA) associatedwith the CdPN; obtain, from a second table, a second MTA associated withthe Cell Site ID; and conclude that the first and second devices arecommunicating in Local traffic, if the first MTA is the same as thesecond MTA.
 17. The server of claim 16 wherein the memory storesinstructions for further causing the processor to: conclude that thefirst and second devices are communicating in Long Distance traffic, ifthe first MTA and second MTA are not the same.
 18. The server of claim16 wherein the first table is provided by a Local Exchange Routing Guide(LERG), and the second table is provided by a Mobile Switching Center(MSC) of a CMRS Provider.
 19. The server of claim 18 including the stepof: storing data in a database, the data tabulated in the first andsecond tables.
 20. The server of claim 16 wherein the memory storesinstructions for further causing the processor to: after concluding thatthe first and second devices are communicating in Local traffic,associate a zero dollar value to the Provider terminating thecommunication from the first device; and after concluding that the firstand second devices are communicating in Long Distance traffic, if thefirst MTA and second MTA are not the same, then associate a dollar valueto the Provider terminating the communication from the first device.